The Board view presents sub-notes in columns for a Kanban-like experience. Each column represents a possible value for a status label, which can be adjusted.

Creating a Kanban board

Right click on an existing note in the Note Tree and select Insert child note and look for Kanban Board.

How it works

When first creating a collection of Board type, a few subnotes will be created, each having a #status label set. The board then groups each note by the value of the status attribute.

Notes are displayed recursively, so even the child notes of the child notes will be displayed. However, unlike the Table, the notes are not displayed in a hierarchy.

Interaction

Working with columns

Working with notes

Working with the note tree

It's also possible to add items on the board using the Note Tree.

  1. Select the desired note in the Note Tree.
  2. Hold the mouse on the note and drag it to the to the desired column.

This works for:

Keyboard interaction

The board view has mild support for keyboard-based navigation:

Configuration

Displaying custom attributes

Since v0.100.0, note attributes can be displayed on the board to enhance it with custom information such as adding a Due date for your tasks.

This feature works exclusively via attribute definitions (Promoted Attributes). The easiest way to add these is:

  1. Go to board note.
  2. In the ribbon select Owned Attributes → plus button → Add new label/relation definition.
  3. Configure the attribute as desired.
  4. Check Inheritable to make it applicable to child notes automatically.

After creating the attribute, click on a note and fill in the promoted attributes which should then reflect inside the board.

Of note:

Grouping by another label

By default, the label used to group the notes is #status. It is possible to use a different label if needed by defining a label named #board:groupBywith the value being the attribute to use (with or without # attribute prefix).

Grouping by relations

A more advanced use-case is grouping by Relations.

During this mode:

Using relations instead of labels has some benefits:

To do so:

  1. First, create a Kanban board from scratch and not a template:

  2. Assign #viewType=board #hidePromotedAttributes to emulate the default template.

  3. Set #board:groupBy to the name of a relation to group by, including the ~ prefix (e.g. ~status).

  4. Optionally, use Promoted Attributes for easy status change within the note:

    #relation:status(inheritable)="promoted,alias=Status,single"